Skip to content

Add note to check liquibase command run correctly#41

Open
ziqing26 wants to merge 1 commit into
TEAMMATES:masterfrom
ziqing26:update-release-pm
Open

Add note to check liquibase command run correctly#41
ziqing26 wants to merge 1 commit into
TEAMMATES:masterfrom
ziqing26:update-release-pm

Conversation

@ziqing26

Copy link
Copy Markdown
Contributor

Outline of Solution

  • Add a note on how PM can check if a liquibase tag is added correctly.
  • Change the instructions from bullet to numbering points for easier reference.

@cedricongjh cedricongjh left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! thanks for updating the docs

@NicolasCwy NicolasCwy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Just one nit from a previous PR which we can correct here too

Comment thread maintainer-guide.md
* [Create an issue for the release](https://github.com/TEAMMATES/teammates/issues/new?template=release.md) to announce the scheduled release time.
* Update the "about page" with the names of new contributors, if any.
* Check if any schema change is needed for this release. If so, inform PM that this release requires maintainance mode and generate Liquibase changelog (refer to [Schema Migration](#schema-migration)).
* Check if any schema change is needed for this release. If so, generate Liquibase changelog (refer to [Schema Migration](#schema-migration)) and inform PM that this release requires maintainance mode.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is maintenance mode needed? I thought that prod should never go down for schema changes, we could correct this here

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hopefully, most schema changes are backward compatible (i.e., no need to go into maintenance mode) but some might not be. So, should cover both cases in the docs.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@damithc schema changes + data migration in SQL is no different than that in Datastore. There is no need for any additional concern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants